The Palomares Incident
Operation Chrome Dome a Cold War Tale of Nuclear Readiness
By Nick Nutter | Published: 2023-07-20 | Updated: 2025-05-20
Visited 6,069 times
Investigating the covert Operation Chrome Dome during the Cold War, where nuclear-armed bombers maintained continuous airborne patrols, ready to strike at any moment. Learn about the challenges, risks, and the legacy of this high-stakes mission that aimed to showcase American nuclear deterrence capabilities and deter potential Soviet aggression.
Contents
Introduction

The Cold War Context
Objective and Execution
Under Chrome Dome, a rotating fleet of B-52 Stratofortress bombers armed with thermonuclear weapons would take off from bases in the United States and fly predetermined routes across the Atlantic Ocean, Arctic, and Pacific regions. These bombers would remain airborne for extended periods, sometimes up to 24 hours, before returning to their bases. On these extended missions the bomber crews could expect to perform in flight refuelling twice, once on the way to their patrol area and once on the return journey. This perpetual state of airborne readiness ensured that a devastating nuclear strike could be launched within minutes, if considered necessary.
Operation Chrome Dome Routes
The Chrome Dome western route passed over Alaska into the Beaufort Sea. Most Alaska tanker crews double turned; flying a mission, landing to upload fuel, and taking off on a second sortie meeting B-52s on 'COLD COFFEE' track.
A Southern European route crossed the Atlantic to a point northwest of Spain. Two tankers from Moron or Torrejón rendezvoused over the Pyrenees Mountains, both bombers gulping down 105,000 to 115,000 pounds of fuel. The B-52s continued to hold points in the Adriatic Ocean off the coast of Italy. Returning to the States, nearing Gibraltar, two more Spain based tankers pumped another 110,000 pounds into each bomber at a location code named 'SADDLE ROCK'.
Tanker aircraft and crews rotated in and out of the US Northeast, Spain, and Alaska Tanker Task Forces on forty-five to sixty-day cycles. Twelve Chrome Dome B-52s remained airborne twenty-four hours a day.
Timespan of Chrome Dome
Challenges and Risks
Moreover, the secrecy surrounding Operation Chrome Dome meant that the American public and even many military personnel were unaware of its existence. There was a great potential for a catastrophic accident that could lead to an escalation of tensions between the United States and the Soviet Union.
The secrecy and risks associated with Operation Chrome Dome eventually led to its demise.
Following the Palomares incident, public scrutiny intensified, and the U.S. government faced mounting pressure to discontinue Chrome Dome. The rapid advancement of intercontinental ballistic missile (ICBM) technology also made airborne patrols less crucial for nuclear deterrence. The final nail in the coffin for Chrome Dome occurred on the 21st of January 1968 when a B-52 carrying four thermonuclear bombs crashed into the sea in North Star Bay, Greenland, causing the conventional explosives aboard to detonate and the nuclear payload to rupture and disperse, resulting in radioactive contamination of the area. In October 1968, after eight years of operation, Operation Chrome Dome was officially terminated by President Lyndon B. Johnson.
Soviet Response to Chrome Dome

United States Bases in Spain

Torrejon Air Base
Moron Air Base
References
2. Palomares Summary Report - Field Command Defense Nuclear Agency Technology And Analysis Directorate Kirtland Air Force Base, New Mexico - 15th January 1975
3. Wikipedia - 1966 Palomares B-52 crash
4. Wikipedia - Palomares Incident
5. Remembering Operation Chrome Dome
Location Map
Enjoyed this history article?
Join our growing community of history enthusiasts, researchers, and discerning travellers receiving regular Mediterranean dispatches directly to their inbox.
Enjoying this clean, uncluttered read?
You are currently browsing the result of a massive technical overhaul. My new book, Legacy Reloaded: A dev, an AI, and the relentless pursuit of 100, chronicles the journey of transforming an aging legacy website into a modern, lightning-fast platform that hits the perfect 90+, 100, 100, 100, 3/3 Lighthouse metrics. It’s a story of collaboration between developer and AI, and the stubborn pursuit of technical perfection.
Read the StoryYou have finished reading chapter 1
More articles in the The Palomares Incident series: